home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-08-22 | 1.9 KB | 44 lines | [TEXT/GEOL] |
- Item 9227273 14-Aug-89 14:12
-
- From: MOOF Rollin, Keith A,APL
-
- To: MACAPP.TECH$ MACAPP Tech
-
- Sub: Re: MacApp to Think Pascal 2.0
-
- Kevin,
-
- This isn't an easy task. There are over 46,000 lines of code in {MALibraries}
- and {MAInterfaces} that need to be converted (Dave Wilson once told be that he
- counted as high as 63,000). There are also three major obstacles that you have
- to get over:
-
- - There is a limit on the number of lines you have in a LSP unit. This has
- to do with the way the LSP debugger works, and can't be changed. This
- limit is also well below the size of most MacApp units (I think the
- limit is 2500 lines; UMacApp.TApplication is 4000 by itself).
- - LSP internally puts all comments at the end of a line (LSP tokenizes as
- you type, which helps makes it so fast). However, the comments it moves
- includes compiler directives, even the ones that NEED to be imbedded
- in the middle of a line (ie, {$IFC qNeedsColorQuickDraw}). Once those
- are moved, you have a different program
- - Segmentation. LSP doesn't recognize the {$S xxx} notation. You would have
- to break apart all the sources and put them back together again in
- the LSP fashion if you want the same segmentation.
-
- Any one of these would make me stay with MPW for compiler MacApp (as a matter
- of fact, it has). However, there was one industrious fellow who DID manage
- porting MacApp 1.1.1 to LSP. He developed a series of scripts for most of the
- work. He talked about it in a past issue of FrameWorks (page 28 of the April,
- 1989 issue).
-
- - Keith Rollin
- - Apple Developer Technical Support
-
- PS: I've seen the new class libraries that come with TC 4.0. There are a few
- little problems we've encountered, but on the whole, they look pretty neat. Job
- Bob says check it out...
-
-
-
-